FrogNet · installation
From a bare Linux box to a fully-configured lillypad — one phase at a time. Nothing joins a network yet; that comes after.
Base configuration
FrogNet runs on hardware you already own.
It asks for three things — Linux, a little memory, and a way to talk.
Base configuration · the OS
A Debian-family Linux base — nothing exotic.
Python, PHP, bash — no unusual dependencies. It runs almost anywhere.
Base configuration · memory
Two gigabytes is the floor.
Enough to run the node, its apps, and the adaptive media loop at once.
Base configuration · interfaces
One interface is required. More is better.
Phase 1
The installer reads the box before it touches it.
Pass, and install proceeds. Fall short, and it tells you exactly why.
Phase 2
This phase needs you online.
Once it's done, the node stands on its own.
Phase 3
Every node gets a permanent name and a fixed address.
Set once, and it is how the node is known from then on.
Phase 4
Tell the node which links it may use. Any mix is valid.
Wired, WiFi, or radio — the node treats them all the same. The link is just a pipe.
Phase 5
How the node offers WiFi depends on what's on eth0.
External WiFi on a Pi: the BrosTrens WiFi 6 antenna is the verified option.
Phase 6
netstart configures the node's networking on every power-on.
The node makes itself ready — before anything else is even in range.
Phase 7 · the end state
A complete lillypad: powered, self-consistent, and alone.
No peers, no broker, no mesh — yet. The moment another node appears, they'll find each other on their own.
You now have one running
You do not need to read the engine or write a line of it. The simulator takes a topology and runs the real discovery, routing and election code against it. Build one that produces a wrong answer and you have found something nobody else did.
Better gets demonstrated, not argued — and the gate does not care who either of us is.